Medway Council
Tree preservation zone
There is a problem
- 93 entries must have dates in YYYY-MM-DD format
entity: 19213992
- reference
- M242-2026
- name
- tree-preservation-order
- tree-preservation-zone-type
- geometry
- MULTIPOLYGON (((0.594247 51.350678,0.594241 51.350674,0.594237 51.350668,0.594239 51.350661,0.594244 51.350657,0.594254 51.350654,0.594262 51.350654,0.594272 51.350657,0.594276 51.350661,0.594278 51.350668,0.594276 51.350672,0.594269 51.350678,0.594258 51.350680,0.594247 51.350678)),((0.594232 51.350645,0.594229 51.350644,0.594223 51.350638,0.594223 51.350631,0.594229 51.350625,0.594239 51.350622,0.594247 51.350622,0.594257 51.350625,0.594263 51.350631,0.594263 51.350638,0.594257 51.350644,0.594247 51.350647,0.594239 51.350647,0.594232 51.350645)))
- point
- POINT (0.59425 51.350651)
- notes
- entry-date
- 2026-08-11
- start-date
- end-date
How to fix this issue
Your data is missing a start-date.
The Tree preservation zone guidance explains how to fix the issue:
start-date
The date that the tree preservation order came into force, written in YYYY-MM-DD format.
Example: 1984-03-28
How to improve Medway Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL